EESSI Governance #456
Merged
EESSI Governance #456
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…we can do that in follow up PRs
|
@casparvl I've fixed some typos in casparvl#1 and casparvl#2. |
fix typo
fix some more typos
|
Oh yeah, thanks, merged! |
ocaisa
reviewed
Jun 18, 2025
docs/governance/governance.md
Outdated
|
|
||
| ### 5.2 Removing Team Members | ||
| <!-- Describe under what conditions someone may be removed (e.g., inactivity, conduct). --> | ||
| Teams decide themselves decide the procedure to remove new Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position. |
There was a problem hiding this comment.
Suggested change
| Teams decide themselves decide the procedure to remove new Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position. | |
| Teams themselves decide the procedure to remove Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position. |
ocaisa
reviewed
Jun 18, 2025
docs/governance/governance.md
Outdated
| TODO: This project follows the [Contributor Covenant](https://www.contributor-covenant.org/) Code of Conduct. | ||
|
|
||
| ## 8. Contribution Agreement | ||
| TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agremeent? If so, that should be stated here |
There was a problem hiding this comment.
Linux projects have a standard approach here which doesn't involve signing a CA
Suggested change
| TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agremeent? If so, that should be stated here | |
| TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agreement? If so, that should be stated here |
There was a problem hiding this comment.
Hm, that sounds attractive, since it means we don't need a lawyer to draw up something for us :)
carefully hand-crafted ... aehm copiloted ... policies
…SSI softwares stack versions and individual software. Remove some duplicate statements
casparvl
commented
Jun 19, 2025
docs/governance/policies.md
Outdated
|
|
||
| - EESSI is committed to providing a complete SBOM for all deployed software. | ||
| - The SBOM should include versioning, licensing, and dependency information. | ||
| - Preferred formats include SPDX or CycloneDX. |
There was a problem hiding this comment.
I'm not sure if we can already meet the latter two points. If not, does it make sense to include them? I don't think so. Or at least we should make clear it's not currently the case, but is a long term goal.
casparvl
commented
Jun 19, 2025
boegel
reviewed
Jun 19, 2025
Co-authored-by: Adam Huffman <[email protected]> Co-authored-by: Bob Dröge <[email protected]>
…r each of the considerations
…ernate for a single meeting, or until further notice
boegel
requested changes
Aug 25, 2025
bedroge
reviewed
Aug 25, 2025
ocaisa
reviewed
Aug 25, 2025
Comment on lines
+68
to
+69
| The EESSI Steering Committee Members are obligated to respect the privacy and | ||
| security of the reporter of any incident. |
There was a problem hiding this comment.
What does "and security" imply? Privacy is easy to understand, but why security? What does that mean?
There was a problem hiding this comment.
Comes from standard contributor covenant, so leaving this as is.
This refers to personal security
trz42
reviewed
Aug 25, 2025
|
|
||
| End users agree to the [Terms of Use](terms_of_use.md) when using the software installations provided by EESSI. | ||
|
|
||
| ## 3. Decision-Making |
There was a problem hiding this comment.
Sometimes we use a dash to bind two words sometimes we don't...
boegel
reviewed
Aug 25, 2025
boegel
reviewed
Aug 25, 2025
Co-authored-by: Thomas Röblitz <[email protected]> Co-authored-by: Bob Dröge <[email protected]>
Co-authored-by: ocaisa <[email protected]>
boegel
reviewed
Aug 25, 2025
ocaisa
approved these changes
Aug 25, 2025
bedroge
approved these changes
Aug 25, 2025
boegel
approved these changes
Aug 25, 2025
casparvl
commented
Aug 25, 2025
boegel
dismissed
verdurin’s stale review
requested changes were either made, or we clarified why the wording is as it is
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To be agreed on by the Steering Committee. I think the most practical is if we keep iterating / wait until every one of us has given an approving review